Skip to content

Fix good job deprecation warning - #1097

Open
zetter-rpf wants to merge 2 commits into
mainfrom
fix-good-job-warning
Open

zetter-rpf wants to merge 2 commits into
mainfrom
fix-good-job-warning

Conversation

@zetter-rpf

Copy link
Copy Markdown
Contributor

This fixes a good job depreciation warning that I saw locally

I've also set up the latest migrations required by good job.

See commits for more

This warning is for use of `good_job_control_concurrency_with`

I've removed the comments that reference it as I think they go into unneeded implementation detail in the tests

[1] https://redirect.github.com/bensheldon/good_job/tree/v4.24.1#migrating-from-concurrency-keys-to-labels
When we upgrade good job, it's good practice to run any new migrations with:

bin/rails g good_job:update
@cla-bot cla-bot Bot added the cla-signed label Nov 6, 2026
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

Test coverage

94.18% line coverage reported by SimpleCov.
Run: https://github.com/RaspberryPiFoundation/editor-api/actions/runs/42253767960

@macroscopeapp

macroscopeapp Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Approvability

Verdict: Needs Human Approval

Macroscope's review found this PR requires human approval — Beyond replacing the deprecated Salesforce concurrency API, this runs substantial shared job-database migrations during release. Confirm production capacity and the deployment/recovery plan, since concurrent index operations still impose database load and can affect existing queues.

Needs human approval because:

  • approvability is in preview mode for this repository, so Macroscope does not approve PRs here

You can add or adjust custom eligibility rules. Learn more.

This branch was successfully deployed

1 active deployment
editor-api-p-fix-good-j-mkxbzp — 60b624de Deployed Nov 6, 2026 by raspberrypiherokubot
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants